Skip to main content
Version: 3.7

Gateways

The Gateways acts as an API control hub. It determines whose traffic is authorized to access the back-end services accessible through APIs. It handles server load by imposing regulations like rate limiting and throttling. It logs all transactions that pass through it and transmits them to servers for analytics and billing purposes.

gatewaymodule

Microgateway​

THAPIM also supports the Microgateway capability. Microgateway allows you to propagate artifact such as Backend, API, Usage Plan, Usage Policy, API Pack and subscriptions to all or a selective gateways.

  • Users can define multiple gateways within a publisher organization.

  • Artifacts such as backends, APIs, packs, usage plans and policies are initially propagated to the default gateway configured for the organization.

  • The Microgateway feature allows users to specify custom gateway configurations for each artifact through the publisher portal.

  • Users can choose to propagate artifacts to a single gateway, multiple gateways, or all gateways depending on their requirements.

  • Dependencies between artifacts are automatically managed.

    • For example: if an API depends on a backend, both will be propagated together when necessary gateways are selected.
tip

An artifact can be propagated to multiple Gateways but a Subscription can be propagated only to one Gateway.